Sometimes people want to be removed from a campaign mailing list. This action is called opting out. Campaign managers want to know the number of people who opt out of a campaign and which source code is related to the opt-out action.
Understanding the tracking of opt-outs helps you analyze the campaign's effectiveness. Opt-outs are tracked from the originating source code so that your campaign manager knows the source code that caused the opt-out action.
Two settings and inserting code into an email template control the opt out configuration:
■ Marketing > Set up module > Opt Out Url field points to a special opt out page, such as http://www.domainname.org/iMIS/OptOut.aspx. When the person clicks on the link in the email containing the Opt Out code, they are taken to this page. The page can contain instructions for choosing to be removed from the list, or request further information for why the message caused the email recipient to choose to be removed.
■ Marketing > Set up module> Opt Out Key field contains %OPTOUTURL% by default. This field contains the code that you insert into the email template in the HTML code. You could change it to %REMOVEME% or another variable name, but you must be sure to change the code in the email templates that use the Opt Out Key in them.
When you create an email merge template, use HTML, not plain text, and use %OPTOUTURL% for the URL for the link. For example, add the text, "If you want to be removed from our campaign, click here." Highlight "click here" and insert a link. Enter %OPTOUTURL% as the URL and choose Other as the Type.
Using this email merge, generate output from a source code. The email messages are generated and sent.
When an email recipient clicks the "click here" link in the campaign email, they go to the URL for the Opt Out Url page configured in iMIS Marketing > Set up module.
If you have more than one source code in one campaign that solicits the same prospect, opting-out for any one source code should opt-out all source codes in the campaign that have solicited that prospect. In addition, iMIS discontinues all further campaign appeals, solicitations, and source codes for that prospect, even those that are created after the opt-out. In short, any future lists automatically exclude that contact from being selected again.
For example, when you look at the Record Responses area and look up an ID, you see every source code the person with that ID is being solicited for. If a member is solicited by two different source codes within the same campaign, they are shown as opted-out of both campaigns.
Solicited and unsolicited responses
The definition of a solicited response is twofold. One definition is an order (product, event, fundraising) or opportunity that has a source code associated with it and the primary contact (or BT_ID) has been solicited for the source code. The other definition is associated with an order that contains no source code but does contain a product that is associated with an appeal and the primary contact (BT_ID) has been solicited for a source code within the appeal. For the second definition to be recognized as a response, automatic source code mapping must be enabled. Opportunities that do not reference a source code are not calculated as a response.
The definition of an unsolicited response is also twofold. One definition is an order (product, event, fundraising) that has a source code associated with it and the primary contact (BT_ID) was not solicited for the course code. The second definition is an order that contains no source code but does contain a product that is associated with an appeal, but the primary contact (BT_ID) has not been solicited for any source codes within the appeal. For the second definition to be recognized as a response, automatic mapping of source codes must be enabled. Auto-mapping of unsolicited responses is not a perfect implementation.
The begin and end dates of the source code, solicitation, appeal, and campaign are ignored when recognizing responses for both explicit or indirect responses. This design means that an order generated past the campaign end date still generates a response to the campaign.
Events and responses
Responses are created as one response per order or event registration. A single event registration for ten contacts would be recorded as a single response.